Skip to content

deps: Update Build Tools #691

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Oct 27, 2025
Merged

deps: Update Build Tools #691

merged 2 commits into from
Oct 27, 2025

Conversation

@renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Jul 22, 2025 •
edited
Loading

This PR contains the following updates:

Package Update Change Age Confidence
cert-manager/cert-manager minor v1.18.2 -> v1.19.1 age confidence
github.com/elastic/crd-ref-docs minor v0.1.0 -> v0.2.0 age confidence
hashicorp/terraform minor v1.12.2 -> v1.13.4 age confidence

Release Notes

cert-manager/cert-manager (cert-manager/cert-manager)

v1.19.1

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

We reverted the CRD-based API defaults for Certificate.Spec.IssuerRef and CertificateRequest.Spec.IssuerRef after they were found to cause unexpected certificate renewals after upgrading to 1.19.0. We will try re-introducing these API defaults in cert-manager 1.20.
We fixed a bug that caused certificates to be re-issued unexpectedly if the issuerRef kind or group was changed to one of the "runtime" default values.
We upgraded Go to 1.25.3 to address the following security vulnerabilities: CVE-2025-61724, CVE-2025-58187, CVE-2025-47912, CVE-2025-58183, CVE-2025-61723, CVE-2025-58186, CVE-2025-58185, CVE-2025-58188, and CVE-2025-61725.

📖 Read the full 1.19 release notes on the cert-manager.io website before upgrading.

Changes since v1.19.0:

Bug or Regression
  • BUGFIX: in case kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed (#​8175, @​cert-manager-bot)
  • Bump Go to 1.25.3 to fix a backwards incompatible change to the validation of DNS names in X.509 SAN fields which prevented the use of DNS names with a trailing dot (#​8177, @​wallrj-cyberark)
  • Revert API defaults for issuer reference kind and group introduced in 0.19.0 (#​8178, @​cert-manager-bot)

v1.19.0

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

⚠️ Known issues: The following known issues are fixed in v1.19.1:

This release focuses on expanding platform compatibility, improving deployment flexibility, enhancing observability, and addressing key reliability issues.

📖 Read the full release notes at cert-manager.io: https://cert-manager.io/docs/releases/release-notes/release-notes-1.19

Changes since v1.18.0:

Feature

  • Add IPv6 rules to the default network policy (#​7726, @​jcpunk)
  • Add global.nodeSelector to helm chart to allow for a single nodeSelector to be set across all services. (#​7818, @​StingRayZA)
  • Add a feature gate to default to Ingress pathType Exact in ACME HTTP01 Ingress challenge solvers. (#​7795, @​sspreitzer)
  • Add generated applyconfigurations allowing clients to make type-safe server-side apply requests for cert-manager resources. (#​7866, @​erikgb)
  • Added API defaults to issuer references group (cert-manager.io) and kind (Issuer). (#​7414, @​erikgb)
  • Added certmanager_certificate_challenge_status Prometheus metric. (#​7736, @​hjoshi123)
  • Added protocol field for rfc2136 DNS01 provider (#​7881, @​hjoshi123)
  • Added experimental field hostUsers flag to all pods. Not set by default. (#​7973, @​hjoshi123)
  • Support configurable resource requests and limits for ACME HTTP01 solver pods through ClusterIssuer and Issuer specifications, allowing granular resource management that overrides global --acme-http01-solver-resource-* settings. (#​7972, @​lunarwhite)
  • The CAInjectorMerging feature has been promoted to BETA and is now enabled by default (#​8017, @​ThatsMrTalbot)
  • The controller, webhook and ca-injector now log their version and git commit on startup for easier debugging and support. (#​8072, @​prasad89)
  • Updated certificate metrics to the collector approach. (#​7856, @​hjoshi123)

Bug or Regression

  • ACME: Increased challenge authorization timeout to 2 minutes to fix error waiting for authorization (#​7796, @​hjoshi123)
  • BUGFIX: permitted URI domains were incorrectly used to set the excluded URI domains in the CSR's name constraints (#​7816, @​kinolaev)
  • Enforced ACME HTTP-01 solver validation to properly reject configurations when multiple ingress options (class, ingressClassName, name) are specified simultaneously (#​8021, @​lunarwhite)
  • Increase maximum sizes of PEM certificates and chains which can be parsed in cert-manager, to handle leaf certificates with large numbers of DNS names or other identities (#​7961, @​SgtCoDFish)
  • Reverted adding the global.rbac.disableHTTPChallengesRole Helm option. (#​7836, @​inteon)
  • This change removes the path label of core ACME client metrics and will require users to update their monitoring dashboards and alerting rules if using those metrics. (#​8109, @​mladen-rusev-cyberark)
  • Use the latest version of ingress-nginx in E2E tests to ensure compatibility (#​7792, @​wallrj)

Other (Cleanup or Flake)

  • Helm: Fix naming template of tokenrequest RoleBinding resource to improve consistency (#​7761, @​lunarwhite)
  • Improve error messages when certificates, CRLs or private keys fail admission due to malformed or missing PEM data (#​7928, @​SgtCoDFish)
  • Major upgrade of Akamai SDK. NOTE: The new version has not been fully tested end-to-end due to the lack of cloud infrastructure. (#​8003, @​hjoshi123)
  • Update kind images to include the Kubernetes 1.33 node image (#​7786, @​wallrj)
  • Use maps.Copy for cleaner map handling (#​8092, @​quantpoet)
  • Vault: Migrate Vault E2E add-on tests from deprecated vault-client-go to the new vault/api client. (#​8059, @​armagankaratosun)

v1.18.3

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

We fixed a bug which caused certificates to be re-issued unexpectedly, if the issuerRef kind or group was changed to one of the "runtime" default values. We increased the size limit when parsing PEM certificate chains to handle leaf certificates with large numbers of DNS named or other identities. We upgraded Go to 1.24.9 to fix various non-critical security vulnerabilities.

📖 Read the full 1.18 release notes on the cert-manager.io website before upgrading.

Changes since v1.18.2:

Bug or Regression
Other (Cleanup or Flake)
elastic/crd-ref-docs (github.com/elastic/crd-ref-docs)

v0.2.0

Compare Source

Changelog

hashicorp/terraform (hashicorp/terraform)

v1.13.4

Compare Source

1.13.4 (October 15, 2025)

BUG FIXES:

  • Fix crash when showing a cloud plan without having a cloud backend (#​37751)

v1.13.3

Compare Source

1.13.3 (September 17, 2025)

BUG FIXES:

  • variable validation: keep sensitive and ephemeral metadata when evaluating variable conditions. (#​37595)

v1.13.2

Compare Source

1.13.2 (September 10, 2025)

BUG FIXES:

  • test: Fix the order of execution of cleanup nodes (#​37546)

  • apply: hide sensitive inputs when values have changed between plan and apply (#​37582)

v1.13.1

Compare Source

1.13.1 (August 27, 2025)

BUG FIXES:

  • Fix regression that caused terraform test with zero tests to return a non-zero exit code. (#​37477)

  • terraform test: prevent panic when resolving incomplete references (#​37484)

v1.13.0

Compare Source

1.13.0 (August 20, 2025)

NEW FEATURES:

  • The new command terraform stacks exposes some stack operations through the cli. Use terraform stacks -usage to see available commands. (#​36931)

ENHANCEMENTS:

  • Filesystem functions are now checked for consistent results to catch invalid data during apply (#​37001)

  • Allow successful init when provider constraint matches at least one valid version (#​37137)

  • Performance fix for evaluating high cardinality resources (#​37154)

  • TF Test: Allow parallel execution of teardown operations (#​37169)

  • terraform test: Test authors can now specify definitions for external variables that are referenced within test files directly within the test file itself. (#​37195)

  • terraform test: File-level variable blocks can now reference run outputs and other variables." (#​37205)

  • skip redundant comparisons when comparing planned set changes (#​37280)

  • type checking: improve error message on type mismatches. (#​37298)

BUG FIXES:

  • Added a missing warning diagnostic that alerts users when child module contains an ignored cloud block. (#​37180)

  • Nested module outputs could lose sensitivity, even when marked as such in the configuration (#​37212)

  • workspace: Updated validation to reject workspaces named "" (#​37267)

  • workspace: Updated the workspace delete command to reject "" as an invalid workspace name (#​37275)

  • plan: truncate invalid or dynamic references in the relevant attributes (#​37290)

  • Test run Parallelism of 1 should not result in deadlock (#​37292)

  • static validation: detect invalid static references via indexes on objects. (#​37298)

  • Fixes resource identity being dropped from state in certain cases (#​37396)

NOTES:

  • The command terraform rpcapi is now generally available. It is not intended for public consumption, but exposes certain Terraform operations through an RPC interface compatible with go-plugin. (#​37067)

UPGRADE NOTES:

  • terraform test: External variables referenced within test files should now be accompanied by a variable definition block within the test file. This is optional, but users with complex external variables may see error diagnostics without the additional variable definition. (#​37195)

Previous Releases

For information on prior major and minor releases, refer to their changelogs:

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested a review from a team as a code owner July 22, 2025 16:07
@renovate-bot renovate-bot changed the title deps: Update module github.com/elastic/crd-ref-docs to v0.2.0 deps: Update Build Tools Aug 20, 2025
@forking-renovate
Copy link

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@panavenue panavenue merged commit 9e60c41 into GoogleCloudPlatform:main Oct 27, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@panavenue panavenue panavenue approved these changes

Assignees

@hessjcg hessjcg

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@renovate-bot @panavenue @hessjcg